Discovery and analytics for episodic downloaded media

ABSTRACT

Matching advertising information to media content/user combinations in which information and content are delivered to a user over a network is disclosed. Content providers and advertisers may find out about the offerings of one another as well as user profiles and preferences thereby facilitating agreement of ads with content and users. Viral syndication is also facilitated by allowing the user to share downloaded media with friends and associates. Users may bookmark, share, and/or request/find more content with similarities to the downloaded content with various analytics being reported with respect to the same.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation and claims the prioritybenefit of U.S. patent application Ser. No. 14/315,694 filed Jun. 26,2014, issuing as U.S. Pat. No. 9,525,902, which is a continuation andclaims the priority benefit of U.S. patent application Ser. No.12/370,531 filed Feb. 12, 2009, now U.S. Pat. No. 8,769,558, whichclaims the priority benefit of U.S. provisional application 61/028,185filed Feb. 12, 2008, the disclosures of which are incorporated herein byreference.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention generally relates to subscription-based receptionof information over a computer network. More specifically, the presentinvention relates to the ‘podcasting’ of media.

Description of the Related Art

Podcasting involves syndicated distribution of multimedia content filesover a network, typically the Internet. Podcasts may be played back onmobile devices or personal computers. Ordinarily, these content filescontain audio or video but may also contain images, text, or other filetypes such as Portable Document Format (PDF).

Syndicated distribution of content is a format used to associatecomputer readable files that are available for delivery over a network.The syndication format is also used to provide users with informationconcerning the subject matter or content of files available fordownload. Based upon information provided through syndicateddistribution, a user may decide to subscribe to delivery of one or morefiles. Syndication format-aware computer programs can, as a result ofthe subscription, automatically determine what files need to bedownloaded to a subscribing user and then automatically download suchfiles as they become available.

A feed is an association amongst files specified in accordance with asyndication format. A feed is generally used to associate filesaccording to criteria specified by a publisher of the content. Filesassociated with a feed, for example, may represent episodes of a programin a manner similar to episodes of a television or radio program (i.e.,episodic media).

A feed may include a list of Uniform Resource Locators (URLs) by whichepisodes of a show may be accessed over the Internet. A content providermay post a feed on a web server. This location (i.e., the web server)may be referred to as the feed Uniform Resource Identifier (URI) or feedURL. A feed is ordinarily updated each time a new episodic media (e.g.,a new episode or media file) is published and made available.Alternatively, a feed may be associated with files based upon morearbitrary criteria such as files corresponding to the favorite songs ofa particular blogger.

The Real Simple Syndication (RSS) and Atom formats are two examples ofpopular feed formats. The RSS format is an example of a simpleExtensible Markup Language (XML) based format that allows users tosubscribe to content available for download from network sites such aswebsites on the Internet. An RSS feed includes an association of filesusing the RSS format. An Atom feed, in turn, operates in a fashionsimilar to that of the RSS format and includes an association of filesusing the Atom format.

A computer program known as an aggregator, which may sometimes bereferred to as a ‘podcatcher’ or podcast receiver, is used to subscribeto and manage subscriptions to feeds. Upon execution of the aggregatorprogram, application, or module by a processor at a computing device,the aggregator monitors a set of feeds for a user. The aggregatordownloads file updates (e.g., new episodes) at a specified interval, forexample, every two hours to the extent file updates are available. Adownloaded file, such as an episode of a television show, can then beplayed, replayed, and/or archived.

RSS, as noted above, is an example of an XML-based feed format thatallows users to subscribe to content provided by their favoritewebsites. Using RSS, a webmaster can host content in a standard fileformat such as mp4 or mp3. The content can then be consumed andorganized through RSS-aware software such as the aforementionedaggregator application.

In accordance with the RSS 2.0 standard, the web address of a file suchas a media file may be contained in an enclosure tag of an item in anXML file. In a similar regard, two constituent elements of a typical RSSfeed are the channel element and the item element. Both the channelelement and the item element may include a variety of sub-elements; theitem element is, in many instances, a sub-element of the channelelement. A channel may contain any number of items. An item may becomplete in and of itself as inclusion of elements in an item areoptional. The following list exemplifies some RSS channel elements witha brief description and example of each element.

TABLE 1 Element Description Example Title The title of the item.Excellent New Song Link The URL of the item.http://publication.com/item. 2006/10/18EAF.html Descrip- Briefdescription The Excellent New Song was of tion the item released tocritical acclaim. Enclosure Description of an Has three requiredattributes. url object attached to indicating where the enclosure is theitem. located, length indicating size in bytes, and type indicates filetype is, e.g. standard MIME type. <enclosure url =“http://www.videoname.com/ mp4s/firstsong.mp4” length = “13217840” type= “video/mpeg” I> Guid Globally unique<guid>http://arbitraiy.server.com/ identifier, a string thatweblogItem5050</guid> uniquely identifies the item. When present, anaggregator may choose to use this string to determine if an item is new.Source RSS channel where the <source item came from. (The url =“http://www.musicreview.org/ purpose of this links2.xml”>moviereview'selement is to propagate location </source> credit for links) DestPointer to location of <dest url = http:// analytics engine. (thewww.myanalytics.com/ma.js purpose of this </dest> element is to enablepublishers to track actual usage of their downloadable media)

Podcasting provides a superior paradigm for delivery of information overcomputer networks. As podcasting has become an increasingly establishedformat for the delivery of audio and video content over the Internet,podcasting has likewise created the need for new mechanisms that operateto the mutual benefit of content owners and consumers. An example ofsuch a need and one that remains unmet by the current state of the artis media metric discovery and reporting.

When a video is played online using a web browser, media usage ismeasured on the connected web server and within the browser embeddedmedia player. In one example involving the Flash media player,Javascript code embedded within the web page is typically incommunication with an online analytics engine such as Google Analytics.

Podcast media, however, is typically downloaded for time-shiftedplayback and off-line consumption. In these instances, a podcast videomight be played using a standalone media player such as iTunes®, whichdoes not typically support the embedding of Javascript along with themedia. iTunes®, too, does not allow for playback measurements to beconnected to an online analytics engine.

The growing popularity of podcasting has created a need to makedownloaded media consumption more easily measurable for content ownersand to create a corresponding set of consumer features around seamlesssharing and discovery of podcasts.

SUMMARY OF THE PRESENTLY CLAIMED INVENTION

Systems and methods for discovery and analysis of episodic media.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system for sharing content amongst users withdisparate means of consumption including devices all the while capturingusage logs for analytics and reporting.

FIG. 2 illustrates a user device including a plug-in for ingestingcontent and feeds and generating data logs for analytics and reportingsystems.

FIG. 3A illustrates an interface to add an RSS content subscription.

FIG. 3B illustrates a graphical user interface (GUI) for a registrationprofile gathering server.

FIG. 4 illustrates a user and usage information gathering system.

FIG. 5 illustrates a system to deliver RSS subscription content to auser

FIG. 6 illustrates a modular architecture coupling a user device plug-into analytics, distribution, media, and campaign management systems.

FIG. 7 illustrates an interface for invoking the sharing of downloadablemedia.

FIG. 8A illustrates a three-button-companion graphical user interface toa user, specifically a highlighted “more” function.

FIG. 8B illustrates a method for operation of a three button companion,specifically the “more” function.

FIG. 9A illustrates a three-button-companion graphical user interface,specifically a highlighted “share” button.

FIG. 9B illustrates the operation of a “share” function in order toemail a video from within a standalone media player.

FIG. 9C illustrates an email message received by a recipient of thesharing action.

FIG. 10 illustrates a three-button-companion graphical user interface tothe user, specifically a highlighted “bookmark” button.

FIG. 11 illustrates an instance of an online video player embedded in aweb browser, where the player allows the user to further share orsubscribe to the video, in addition to playing the video.

DETAILED DESCRIPTION

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

Embodiments of the present invention concern a system and method formatching selected information, such as advertising information, to mediacontent/user combinations in which information and content are deliveredto a user over a network. Such embodiments may facilitate an onlinemarketplace in which providers of media content and ad providers matchads with content and with online users who receive or subscribe toreceive the content. The online marketplace may provide a venue in whichcontent providers and advertisers can find out about the offerings ofone another user profiles and preferences thereby facilitating agreementof ads with content and users.

Content providers provide media content, which may comprise sound,motion pictures, or a combination of both. A motion picture mayrepresent real-life images or computer generated images such as videogame environment. Media content may comprise music, news reports, talkshows, weather reports, traffic reports, video dips, and radio/TV likeprograms, which may be referred to as episodic media.

Media content may be organized into periodically updated contentchannels. A talk show channel, for example, may be updated with thelatest interview. A weather channel may be updated with a new weatherreport. Content providers may use a network such as the Internet todesignate criteria for associating their content with ads.

Computer Code Table A, which appears prior to the claims, identifiescomputer program code that may be used in the implementation of someembodiments of the present invention. The “Get Podcast” code comprisesautomatically generated JavaScript that can be attached to a contentprovider's web site to provide a link that permits visitors to thecontent provider's web site to easily sign up for the contentsubscription service, and install media player plug-in software thatenhances discovery and sharing of downloaded subscription media.

FIG. 1 illustrates a system 100 for sharing content amongst users withdisparate means of consumption including devices all the while capturingusage logs for analytics and reporting. An advertiser 101 feeds thesystem 100 with advertisement media content and campaign rules governingdistribution of that content. Publisher 102 feeds the system 100 withinformation and/or media content, which may include episodic media(e.g., video clips, series of interviews, and other multimedia content)along with associated metadata.

Central Service Provider 105 matches ad media with content media.Matching of content media from publisher 102 may be matched withadvertisement content from advertiser 101 based on the campaign rulesprovided by advertiser 101. For example, an advertiser may desire tohave their advertisement content (e.g., for a sporting goods store)inserted only in the context of sports related content (e.g., a baseballgame). The Central Service Provider 105 inserts the advertising mediafile within the content media file to create a newly modified,ad-infused media content file. Such insertion process may requirere-encoding (e.g., transcoding) the advertising file, the content file,or both the advertising and content file to a uniform matching profile.Central Service Provider 105 may be a single operating entity or a looseaffiliation of or wholly unaffiliated group of computing devices and/orsoftware applications offering ad matching and related services.

Once a uniform matching profile is created, the content file is splitinto two parts: Part I and Part II. The split occurs at the locationwhere the advertisement is to be inserted. For example, a content filemay be split 1 minute from the start of a video that is 30 minutes long.Part I is now 1 minute long whereas Part II is 29 minutes in length. Theend of Part I of the content file is then stitched to the beginning ofthe advertisement file and Part II of the content file is stitched tothe end of the advertisement file thereby creating the ad-infusedcontent file. Any number of ads can be inserted into any number oflocations within a content file. As such, a content file may be splitinto any number of parts or segments.

Several variants of the modified content file may be created therebyaddressing different types of content. For example, sporting goodadvertisements may be ‘stitched’ into football content whereas feminineproduct advertisements may be introduced into women oriented content.

Other variants may also be created through a similar re-encoding processto address compatibility for different types of devices. For example, asmaller phone screen may require a different encoding format than a fileformatted for a personal computer screen. The modified content file maythen be made available for delivery on a content hosting server at theCentral Service Provider 105.

Modified content downloaded from a hosting server at Central ServiceProvider 105 may be consumed by a variety of devices with any variety ofdevice settings. For example, content may be consumed at a personalcomputer (140) by a user utilizing a web browser to visit a websitethrough entry of a URL and selecting a ‘play button’ in an embedded webmedia player. The user may then immediately start watching the videocontent file stored on a content hosting server.

Another user, however, may manually or automatically download a versionof this same video file to a standalone media player (130). An exampleof such a standalone player is the podcast application software found iniTunes®. The user may also watch the video at a later time bydownloading the file in a format for a particular mobile media device(150).

Still other users may watch content through a web-based media playerembedded in a social networking site (160) such as MySpace. The socialnetwork site 160 may not actually host the content notwithstanding thefact that the content may be viewed at the site. For example, the actualhost of the content may be YouTube. MySpace may operate as a portal thatembeds content otherwise hosted on a YouTube server. For example, adesigner of the social network site portal may use an embedded sourcecall as follows, which not only retrieves the content from a server atthe Central Service Provider 105 but also calls for the content to berendered in a Flash media player:

-   -   <embed src=“http://www.youtube.com/v/B2qo2bV1ORc&h1=en&fs=1”    -   type=“application/x-shockwave-flash” allowscriptaccess=“always”    -   allowfullscreen=“true” width=“480” height=“295”></embed>

But for the presently disclosed system 100, this fragmentation ofaudiences and media consumption behavior might otherwise be problematicfor publishers 102 and advertisers 101 who each desire to seamlesslyreach audiences of scale without having to deal with the intricacies andpeculiarities of each platform. Such peculiarities, for example couldinclude video formats and encoding resolution. The system 100 of FIG. 1addresses this problem by automatically encoding and transcodingpublisher 102 and advertiser 101 content such that it is compatible withdifferent platforms.

Further illustrating this disparity amongst users and means of contentconsumption- and thus further highlighting the benefits of the presentinvention-a user operating with standalone media player 130 might sharea video via email 131. The recipient of the email 131 may watch thevideo in a web media player 140 at, for example, a website operated bythe content owner. Some recipients of the email 131 could decide todownload 141 the video to their standalone media player 130 while othersmight decide to showcase the video within a web video player on theirsocial network profile page 160 using embedded code 143. Still othersmay decide to email 142 the video to their friends who would thenreceive the email on a mobile media device 150 such as an iPhone, whichincludes one or more built-in media players. A visitor to the socialnetwork site 160 may find the displayed video entertaining orinformative and elect to subscribe (or immediately download) 161 to thecorresponding channel in order to automatically receive subsequent andfuture updates of the content in their standalone media player 130.Another user, still, could bookmark 144 (or embed) the content atanother site having a web media player (140) such as a personal websiteor a website associated with bookmarked content.

Movement of consumption of a single video multiplied by the millions ofusers consuming thousands of videos on tens of different platformsresults in the aforementioned need for a comprehensive measuringanalytics and reporting system for publishers 102 and advertisers 101.The present invention may capture media usage from a variety of mediaplayers 130, 140, 150, and 160 and corresponding content servers (e.g.,servers as Central Service Provider 105) for analysis and creation ofinsightful reports. Such data may be stored at database 170.

Irrespective of how content is consumed, usage measurements may be madewhen the content is consumed. Standard web logs may provide measurementsof content downloaded from the hosting servers at Central ServiceProvider 105. Playback logs may also be maintained and acquired fromeach of the aforementioned media players/device (130, 140, 150, and160). Reports may be generated based upon all captured events and storedin aforementioned database 170.

These reports are made accessible via an online analytics and reportingportal 180. These reports may be accessed by publishers 102 andadvertisers 101 to make determinations concerning the success ofadvertisement campaigns, the desirability of content, and the success ofintegrating the two forms of content (ads andentertainment/information). Portal 180 may present data from database170 to publisher and advertiser accounts as part of a singlecomprehensive account in order to manage the entire information aboutthe content as well as schedule ad campaigns.

FIG. 2 illustrates a user device 200 including a plug-in 220 applicationfor ingesting content and feeds and generating data logs for analyticsand reporting systems. User device 200 is inclusive of any devicecapable of acquiring and allowing for consumption of content. Forexample, user device 200 may be a mobile device 150 as referenced inFIG. 1. User device is also inclusive of computing devices operatingmedia players/browser devices 130, 140, and 160 in FIG. 1 as well asuser device 406, as that device is discussed in the context of FIG. 4.Plug-in application 220 is a lightweight software application executableby the processor of a computing device such as user device 200. Plug-inapplication 220 may encompass various subsidiary software modules suchas reporting module 235, content assembler module 223, and requesthandler module 221.

The content and feed servers 210 may be part of the central services 105as referenced in FIG. 1 or may be hosted elsewhere. Content servers hostthe media file and serve the content upon receipt of a request generatedby execution of the request handler module 221 contained in the plug-inapplication 220. The feed servers hold the RSS feed, which is a textfile in XML format. A podcast application, such as iTunes, will receivethe feed from the feed server at the time of subscription. The RSS feedholds information on the location of the media file hosted on thecontent server.

Execution of the plug-in application 220, generates the aforementionedrequest for the RSS feed. The application 220 then transforms deliversthe modified feed to the podcast application thereby resulting in theaddition of a channel subscription. Execution of the plug-in application220 offers the user enhanced mechanisms to easily discover and shareattractive content through a graphical user interface, while managingcontent and feeds alongside the media player and collecting preciseusage (e.g., playback) events from the corresponding media player. Theusage events are then delivered to a reporting and analytics service 250via a communications network 225 such as the Internet for furtheranalysis. The usage data could also be sent to multiple reportingservices; each RSS feed may specify data to be sent to a differentreporting service.

Execution of the content assembler 223 causes the plug-in application220 to receive content from a publisher 102 or content server 506 (asillustrated in FIG. 5), advertisements from an advertiser 101 oradvertising server 505 (also illustrated in FIG. 5), and insert theadvertisement into the content to create an ad infused media file.Expired advertisements, too, may be removed with a new advertisementinserted in its place. Content assembler 223 splits the content fileinto two parts as described above whereby the end of a first part of thecontent file is stitched to the beginning of the advertisement file andthe second part of the content file is stitched to the end of theadvertisement file. The content assembler 223 can assemble any number ofads into any number of locations within a content file.

The reporting module 235 of the plug-in application 220 is executed atthe user device 200/406 to collect media usage data. When reportingevents to a usage information gathering server 250 (also illustrated asserver 403 in FIG. 4), usage data may be associated with a unique UserID. The User ID may be generated and issued by the usage informationgathering server 250/403. The User ID allows the server 250/403 tocorrelate usage to user while maintaining anonymity and privacy of theactual user. The usage information gathering server 250/403 furtheraggregates user and usage logs including data from the content serverand feed server web logs. Aggregated data may be maintained at adatabase 255, which also corresponds to the database 170 of FIG. 1.

The following list exemplifies events collected and sent to a usageinformation gathering server

EVENT CODE episode download success cc episode download failure cechannel subscribed af initial add feed ia episode play pl episode playcount pc episode play count on device pd ad playback vl ad full playbackvc buttons shown bs share episode sh share view sv bookmark episode bmbookmark view bv open more tab mo

FIG. 3A illustrates an interface to add an RSS content subscriptionwhereas FIG. 3B illustrates a graphical user interface (GUTI) for aregistration profile gathering server. The GUIs of FIGS. 3A and 3B maybe used by the user device 406 of FIG. 4 (and the user devices ofFIG. 1) to interact over a network 225 (as illustrated in FIG. 4) with aregistration profile gathering server 402.

FIG. 3A illustrates that the content provider web page may includevarious information and a “Get Podcast” button, which may have beenadded using the copy and paste process set forth in the computer codelisted in Table A. Upon a user actuating the “Get Podcast” button on theweb site of a content provider or on the web site of the intermediary,the browser is redirected to a web page of the intermediary site thatprovides the registration information request shown in FIG. 3B.Registration information may generally include user attributeinformation but is also inclusive of requests for user acceptabilityrules that indicate the kinds of information that the user does and doesnot want to receive. User acceptability rules can be used to recommendparticular types of content. While only one user registration screen isillustrated in FIG. 3B, more than one screen may be used.

Following a subscription process, which may take place through theinterface illustrated in FIG. 3A, the plug-in application (220 of FIG.2) is downloaded from a software download server such as a web server.Once the plug-in application 220 has been installed and executed for thefirst time, the application 220 triggers a request to the user toprovide user profile information via an interface like that illustratedin FIG. 3B.

User profile information may be provided via the user device 406 of FIG.4 (or a corresponding user device as illustrated in FIG. 1) over thenetwork 225 to the registration profile gathering server 402. Theplug-in application then downloads content from a content server (e.g.,content server 506 of FIG. 5). Content server may be any content serverspecified in an RSS feed subscribed to by a user. A JavaScriptsubscription function (e.g., the VoloMediaSubscribe ( ) function ofTable A) is run on the user device 406 and ensures that the user device406 has the client-side plug-in application installed. The actionsinitiated by user actuation of the Get Podcast button of FIG. 3A includechecking if the plug-in application module is installed. If the plug-inis not installed, an installation file is downloaded and executedfollowed by a registration process.

FIG. 4 illustrates a user and usage information gathering system 400. Auser 405 operates a user device 406, which is inclusive of personalcomputers, personal digital assistants (PDAs), an iPod from Apple Inc.or other portable media devices such as a PlayStation Portable from SonyComputer Entertainment Inc., which permits the downloading of contentover a network 225 such as the Internet. System 400 gathers userregistration profile information when user 405 first registers toreceive certain content. In addition, the system 400 periodicallygathers user usage information indicative of content and advertisementsobtained or subscribed to by a user.

User registration profile gathering server 402 gathers user profileinformation over the network 225 during user registration. Server 402may be a web page server that serves up web pages to a browser enableduser device 406 over the network 225 to solicit user preferences and/orrules during registration of the user 405. Usage information gatheringserver 403 periodically gathers user usage related information over thenetwork 225.

In one embodiment, a user device 406 runs an application 407 (e.g.,plug-in application 220) that gathers usage information and periodicallyuploads that information over the network 225 to the user usageinformation gathering server 403. The usage information upload may beautomated thereby obviating the need for user interaction.

The system 400 also includes a storage repository 404 to storeuser-related information. The user-related information may include useracceptability rules 404 a that express preferences of user 405. Suchpreferences may be absolute such as what type of information a userabsolutely does or does not want to receive. Alternatively, rules 404 amay be flexible and merely indicative of preferences.

The user-related information may also comprise user attributes 404 bthat express user qualities or characteristics. User attributes maycomprise gender, age, listening and/or viewing habits of a user.Attributes may further include geographic information such as zip codeor whether or not the user 405 has children.

FIG. 5 illustrates a system 500 to deliver RSS subscription content to auser. System 500 may combine ad campaign provider ads into contentprovider content. A web page 502 is displayed by a PC web browser. Theweb page 502 is associated with a content provider. A content providercontent server 506 serves content in response to RSS feed requests.

At time=t1, a user actuates a link on web page 502 to request an RSSfeed associated with content served by content server 506. In responseto the request, at time=t2, the RSS feed is delivered over the network225 to the podcast application 504.

A transform function 510, which is a part of the plug-in application 220running on the user device (user device 406 of FIG. 4) receives the RSSfeed and changes all content URLs to point to local host (127.0.0.1). Attime=t3, the RSS feed with the transformed URLs is delivered to thepodcast application 504, such as iTunes® running on the user device. Thecontent provider web page 502 includes a “get podcast” button associatedwith JavaScript used to download the plug-in 220 like that discussed inthe context of FIG. 2 and acquired via an interface like that of FIG.3A. When a user selects the “get podcast” button, the user is asked forpermission to install the plug-in client 220 if it was not previouslyinstalled. If the client has already been installed, the client takescontrol and adds the feed to the podcast application 504.

At time=t4, the podcast application 504, such as iTunes initiates anupdate of content associated with the RSS feed. The request isintercepted by the request handler module 221 of the plug-in application220 illustrated in FIG. 2. Request handler 221 includes a listener onlocal host (127.0.0.1), which ‘listens’ on the local host IP 127.0.0.1and intercept calls by the iTunes® application or any other mediamanager application.

At time=t5, the request handler module 221 forwards the interceptedrequest over the network 225 to a content server 506. At time=t6, thecontent server 506 receives the request sent by the content assemblermodule 223, which is also illustrated in the context of the plug-inapplication 220 of FIG. 2. At time=t7, the content server 506 returnsthe requested content over the network 225 to the content assemblermodule 223.

At time=t8, the content assembler module 223 receives the requestedcontent update. At time=t9, content assembler module 223 insertsadvertisements into the newly arriving content if an advertisement isavailable to be inserted. At time=t10, the original content or themodified ad infused content is streamed to be played or to be stored asa content file for later playback in the podcast media playerapplication 504.

The original RSS XML is transformed by the management plug-in (afterdownload) to point all the URLs of the files, such as content files, tothe “local server” (127.0.0.1) so that all podcast manager applicationcontent requests for this RSS will be directed to and handled by theplug-in (client application). The podcast management plug-in listens ona local host port and intermediates in content requests by the podcastmanager application. Each RSS feed may represent a podcast content feedwith a list of episodes. In one example, there exists one RSS feed perpodcast subscription, which is similar to a virtual channel. Theclient-side plug-in intervenes each time the user clicks on a “GetPodcast” button for each feed by rewriting address elements within eachRSS feed (e.g., changing address to 127.0.0.1:port) before handing itoff to the podcast manager application. For example, if a usersubscribes to 100 feeds/channels, then there are 100 RSS feeds for whichthe client-side plug-in intervenes.

The podcast manager application requests a file from the RSS feed. Themanagement plug-in intercepts the feed request, which has been modifiedto point to the request to the local host. The management plug-in,rather than the podcast manager application, forwards the request forthe file indicated by the RSS feed. The plug-in generates a new httprequest for the file from the server such as the content server 506. Acontent server that hosts the content can be either hosted within thecentral services provider 105 of FIG. 1, by a content provider, or by anintermediary. The plug-in intercepts file requests from the podcastmanager application (to 127.0.0.1:port) and rewrites each such requestso that the content server 506 receiving the request sends requestedcontent back to the management plug-in rather than sending it directlyto the podcast manager application.

The following is an illustrative example of the intermediation of themanagement plug-in application in the retrieval of a content feed. Auser requests that a content feed be added by clicking an icon on a userdevice interface. The request is captured by the management plug-insoftware, which changes the original URL of the file in the RSS feed.For example, http://www.somesite.com/podcast/channels/morningnews.mp4may be changed to http://127.0.0.1:10930/?getitemwww.somesite.com/podcast/channels/momingnews.mp4. The full original URLof the file is stored as an argument after the “getitem_.” Subsequently,a user may request a file from that RSS feed. Thus, the podcast manageruses the changedURL—http://127.0.0.1:10930/?getitem_www.somesite.com/podcast/channels/mo-mingnews.mp4to actually make the call for the file. The plug-in software remainslistening on the address 127.0.0.1:10930, however. The plug-in capturesthe request and generates a request to a content server that serves therequested RSS feed, using the original URL that is stored as an argumentafter the “getitem_.” (i.e.,www.somesite.com/podcast/channels/momingnews.mp4). Alternatively, theplug-in application could also be implemented and directly used on userdevices with Internet Protocol (IP) capabilities. These devices do notneed to use an intermediate podcast manager application (e.g., iTunes)for content syncing as they can obtain the RSS and the content directlyfrom the network, such as the Internet.

FIG. 6 illustrates a modular architecture coupling a user device plug-in220 to analytics, distribution, media, and campaign management systems.In one example, a plug-in application 220 operating in an iTunes®environment determines when an episode or advertisement has played andreports such data to other subsystems. The plug-in reporting module (235of FIG. 2) logs data about the played file along with data concerningthe starting offset and duration of the playback event. Reporting module235 further analyzes the advertisements that were inserted into thecontent file to determine which advertisements and content were viewedby the user.

In the present example, the plug-in reporting module 235 makes use ofthe iTunes® music library xml file to determine the play counts for anygiven episode. By keeping track of the playback events from thereporting system and looking at the playback counts listed in theiTunes® music library file, the plug-in is also able to determine howmany times an episode was played on a corresponding iPod device. Usingapplication interfaces built on the HTTP protocol, the plug-inapplication 220 can communicate detailed iTunes® playback data toexternal advertising systems 610 such as Doubleclick's DART or any otherthird party reporting system 600 (e.g., reporting and analytics systems180 of FIG. 1).

The location of the analytics and reporting system may be specified inthe form of a URL included in an RSS feed item element. The URL pointerto the analytics and reporting system may likewise (and in a real worldimplementation) be passed on to the plug-in application 220 as anargument to the VoloMediaSubscribe( ) function as referenced in Table A.The RSS feed of the subscribed channel is an argument to theVoloMediaSubscribe( ) function call from Table A. Usage data, includingplay events, related to the RSS feed is sent over HTTP protocol to theanalytics and reporting system. In a still further example, the locationURL of the reporting system is specified within the header of the mediafile.

Some embodiments of the present invention include providing for viralsyndication by allowing the user to share downloaded media with friendsand associates. Sharing may take place through a graphic or text overlayassociated with the downloaded content. The overlay may indicate optionsfor bookmarking, sharing, and/or requesting/finding more content withsimilarities to the downloaded content.

Embodiments of the present invention may be integrated with variousbookmarking services, email services, and media player environments. Ifa user chooses to bookmark a media file, the user may be presented witha menu of bookmarking services associated with the user. The user maythen designate a particular bookmarking service (e.g., Google Bookmarks)and information concerning the bookmark may automatically be sent to theuser account on the bookmarking service. Bookmarking may include storingand retrieving information concerning the website from which the contentwas downloaded, inviting friends to view the bookmarked (favorite) videodips, and copying and sending such information to various other bookmarkservices such as Google Bookmarks, del.ici.ous, and Digg.

If a user wishes to share a media file, emails with informationconcerning the media file (e.g., media URLs) may automatically begenerated to send to friends and associates. Sharing the content mayalso include sharing the bookmark or ‘pushing’ the downloaded contentback onto the Internet. If the user requests similar content, thesimilar content may be delivered to the particular media environment inwhich the user made the request. For example, the user may be watching avideo file on iTunes® and request content similar to that of the videofile just consumed. Similar content may then be added to iTunes®including a subscription. The information concerning sharing,bookmarking, and searching for similar content may be captured andanalyzed for reports to advertisers and/or content publishers.

Publishers or content owners may likewise recommend similar content tousers. For example, a user may watch a program from ABC News. Apublisher or content provider (which may be the host of the ABC Newsprogram) may identify similar content, individual shows, or channels andrecommend the same. Recommended content may then be added to aparticular media environment (e.g., iTunes®) for downloading by clickinga single button or added as a RSS subscription when a channel isrecommended. Publishers may recommend content to users who may or maynot be connected to the Internet or those users who are not currentlyvisiting the website of the content provider. Publishers may alsorecommend content to users based upon their demographic information(e.g. age, gender, or location) or upon their behavioral information(e.g. types of content the user watches).

Sharing of content initiated at one platform such as iTunes®. butconsumed on another platform such as through a Flash video player whilepreserving an advertiser's and/or publisher's ability to present freshlyinserted advertisements at the time of consumption are further providedby embodiments of the present invention. A podcast publisher maylikewise track the consumption of a video or other content file whenplayed within a standalone media player such as iTunes® by using anyonline web based analytics and reporting engine. The movement andconsumption of video files from downloads to online, across differentonline locations, and from online to download may be tracked thusproducing detailed analytics of the movement and consumption of media.

FIG. 7 illustrates an interface for invoking the sharing of downloadablemedia. When a user wishes to share, bookmark, or find other relatedvideos, pressing the pause button is a first step to invoking sharingand discovery functions. FIG. 7 illustrates an invitation to a userconsuming the content to press the “pause” button to triggerpresentation of a three-button-companion interface.

FIG. 8A illustrates a three-button-companion graphical user interface toa user, specifically a highlighted “more” function. Through thisinterface, which may be displayed to a user on a corresponding userdevice (for example, user device 406 of FIG. 4), a user may obtainrelated information or recommendations based upon metadata in a currentcontent file or information within a corresponding RSS feed. Theinterface allows the related information or recommendations to beobtained over a network while the user is downloading the content orwhen the user has cached the content for later use when the user isoffline as is discussed with respect to the FIG. 8B. The interface ofFIG. 8A is, in one embodiment of the present invention, displayed to theuser when the user pauses the media file in the context of FIG. 7.

FIG. 8B illustrates a method for operation of a three button companion,specifically the “more” function. The flow diagram also depicts theability of the system to notify the user if a given action requiresnetwork connectivity and to act upon that action once the user returnsto an online state. In step 810, the interface (like that of FIG. 8A) islaunched. Launch of the interface companion may occur as a result ofselecting ‘pause’ as discussed in the context of FIG. 7. A determinationis then made, in step 820, as to whether the user is on-line oroff-line. RSS, images, and “more” content are downloaded and cached instep 830 for current and/or later display if it is determined that theuser is on-line. If the user is determined not to be on-line, previouslycached content is displayed in step 840. If the user initiates an actionthat otherwise requires an on-line connection (step 850), then thebrowser or media application (e.g., iTunes®) will display an appropriatemessage indicating the present off-line state in step 860. Should therebe a state change with respect to connectivity as determined in step870, the appropriate steps of the flowchart are then followed.

With respect to steps 830 and 840, the interface is populated with bothrelated information as well as recommendations that are obtained eitherfrom the network or from a local cache that was obtained while the mediafile was being downloaded. The location of the related information andrecommendations may be specified in the form of a URL included in an RSSfeed item element. Both the related information and the recommendationsmay themselves contain metadata that allows a user to further act uponthe information.

In one example, selecting related information or a recommendation maycause the user device to download additional media files from thenetwork. In another instance, selecting the related information orrecommendation may cause the user device to display additionalinformation about the media file. This additional information may be inthe form of a web page that is displayed on the device or the additionalinformation could be displayed in the form of a graphical user interfacelaid over an existing interface. Metadata that would cause additionalmedia files to be downloaded may be labeled ‘Get’ and metadata thatwould cause additional information to be displayed would be labeled‘Go’. Examples of both types of metadata are illustrated in FIG. 8A.

Interactions of the user with the user device may immediately be sentover the network to a usage information gathering server (such asgathering server 403 of FIG. 4) or can be locally cached to be sent at alater time. Examples of the actions that could be sent include the userselecting the ‘More’ interface element to display related informationand recommendations. Other examples of actions that could be sentinclude the user selecting a ‘Go’ or ‘Get’ interface element.

A URL location pointer passed on to the plug-in application as anargument in the VoloMediaSubscribe( ) function and illustrated in TableA is invoked on selection of the ‘More’ interface element. Selection ofthe ‘More’ interface element invokes a URL included in the RSS feed asan item element. The ‘More’ URL may be specified within the header ofthe media file. Selection of the ‘Get’ interface element by the user mayadd an associated RSS feed as a new channel subscription.

FIG. 9A illustrates a three-button companion graphical user interface,specifically the highlighted “share” button. The “share” button allowsfor the emailing of a video from within a standalone media player. Inthe interface of FIG. 9A, the user is presented with a form userinterface that includes fields to list recipient email addresses, thename and email address of the user sending the content, and a message.In this example an optional captcha form is included to help validatethat the user is a valid person and not a computer program.

FIG. 9B illustrates the operation of a “share” function in order toemail a video from within a standalone media player. Additionalinformation may also be shared through this methodology, the additionalinformation may include but not being limited to the original URL forthe media file, the feed URL for the show where the media fileoriginated, the title of the show, the title of the media file, and asubject and message included by the user.

In step 910, a user clicks on a share button, which may be similar tothe button illustrated in FIG. 9A. A window is then launched in step 920whereby a user is prompted to provide information for e-mailing thevideo or other content. In many instances, the content itself is notsent due to bandwidth constraints. Instead, a link identifying andallowing for access to the content is sent. The user fills out the formin step 930 including an e-mail address of the recipient, that of theuser, and/or a note for the recipient that is to accompany to thecontent being delivered to the recipient. The message is sent throughthe clicking of a send button on step 940. Instead of an e-mail address,other forms of contact information may be used including an instantmessaging address or cell phone number.

If all fields from the popup window displayed in step 920 are determinedto have been correctly filled out at step 950, the message is sent instep 960 along with a Globally Unique Identifier (GUID) and metricsinformation. The GUID information is requested by a backend log in step970. The GUTID and IP address of sender may be applied against a spamdatabase in step 980 such that a determination may be made at step 990as to whether the message being sent is legitimate or unwanted spam. Ifthe message is determined to be spam, delivery fails and a correspondingdelivery failure message is displayed. If the message is determined notto be spam, then the content and corresponding message is sent alongwith an indication that delivery is successful.

Returning to step 950, if it is determined that all fields have not beencorrectly filled out (e.g., an email address of the recipient or senderis omitted), then the process returns to step 930 to correct theerroneous information. An indication as to the error might be reflectedin step 995. Different fields may be necessary to allow for delivery ofcontent or a link to the same. Other fields may be optional wherebyincorrectly provided information does not otherwise prevent delivery ofthe content.

As noted above, additional information may be sent with a media file ora link thereto. Additional information may be obtained by parsing themedia file and extracting information from the metadata within the mediafile. The additional information may also be obtained by parsing the RSSfeed from which the media file originated or receiving the informationdirectly from the user. The additional information could also beobtained by using any combination of the three methods. Once theadditional information is obtained, the system may share the media fileand information in a manner similar to that described above in FIG. 9B.

FIG. 9C illustrates an email message received by a recipient of thesharing action. The message could include links to play back the mediafile as well as a link to report that the shared media was received inerror by the recipient user. Before sending the media file andadditional information to the recipient, the information can beformatted to be properly displayed on the recipient user's device. Ifthe recipient address was an email address, the information could beformatted to include a snapshot from the video file along with a link toview the media file in a web browser. In another example, the messagecould be formatted to embed a video player so that the recipient usercould directly view the media file in the message. A URL link to a pagecontaining the embedded shared media could also be sent to therecipient. The recipient may be able to view the shared media within anembedded media player contained in a web browser.

FIG. 10 illustrates a three-button companion graphical user interface toa user, specifically a highlighted “bookmark” button. Bookmarking thecontent file and/or additional information allows for the content andinformation to be bookmarked to one or more social bookmarking websites.The additional information can include but is not limited to theoriginal URL for the media file, the feed URL for the show from wherethe media file originated, the title of the show, the title of the mediafile, tags associated with the media file or show, or a message includedby the user. Additional information may be obtained by utilizing any ofthe aforementioned methodologies including parsing the media file or theRSS feed as well as receiving information directly from a user.

Through the interface of FIG. 9C, the user may select one or more socialbookmarking websites on which to bookmark the media file and additionalinformation. The system determines the parameters that need to be passedto each site in order to allow the information to be bookmarkedproperly. When the user is on-line, the information can be sent directlyto the social bookmarking site using the network. When the user isoff-line, the system can cache the information to be sent when the userreturns to an on-line state. Examples of social bookmarking sitesinclude but are not limited to Digg, Google Bookmarks, and StumpleUpon.

Once placed on the social bookmarking site, the bookmark enables theuser or other users to directly download the media file without firstrequiring the RSS feed or show subscription. The bookmark also enablesusers to gain access to media files that have since been removed fromthe RSS feed. In another related embodiment, embed code may be generatedwith information extracted from parsing the RSS file or the media file.The embed code, when manually pasted or automatically uploaded to apersonal user profile page on a social media site, a web media playercontaining the embed video is generated at the social media site.Examples of social media sites include but are not limited to Facebook,Myspace and Tagged. The user may be required to input login and passwordinformation for their social network account in order to upload thecontent or information.

FIG. 11 illustrates an instance of an online video player 1100 embeddedin a web browser, where the player allows the user to further share orsubscribe to the video, in addition to playing the video. To view videowithin such a web media player 1100, a user is not required to install astandalone media player or the plug-in software. An online embeddedvideo player 1100 as illustrated in FIG. 11 contains certain viralsharing features as ‘built in’ functions whereby users may invite otherusers to view the video or embed the video on their social mediapersonal profile pages. The embedding of the video may be accomplishedmanually or automatically by copying the embed code 1130 and pasting itin social media profile pages.

FIG. 11 also illustrates an additional feature allowing web users to getthe channel feed as a subscription download 1120. This feature may proveuseful for those users that prefer to have the media automaticallydownloaded to their device on a periodic basis instead of having toactually visit websites to receive periodic updates to content of theirinterest. Downloaded content is consumed using a standalone media playersuch as iTunes® and can become portable on non-networked portable mediadevices such as the ipod allowing usage even while a user is offline.

In one exemplary embodiment, users may share their favorite videos withfriends and family via email using the ‘share this clip’ link 1110. Inanother embodiment, users may embed the web media player 1100 containingepisodes and channels they wish to share with friends, family, andvisitors to their profile pages from within the standalone media playerrunning on the user device. This may be accomplished by automaticallywriting the related embed code or bookmark links to the users profilepage. The user may be required to input login and password informationfor their social network account. These sharing mechanisms enable viraldiscovery of media and fast adoption of popular media because ofuser-to-user remarketing.

Computer-readable storage media refer to any medium or media thatparticipate in providing instructions to a central processing unit (CPU)for execution. Such media can take many forms, including, but notlimited to, non-volatile and volatile media such as optical or magneticdisks and dynamic memory, respectively. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROMdisk, digital video disk (DVD), any other optical medium, RAM, PROM,EPROM, a FLASHEPROM, any other memory chip or cartridge.

Various forms of transmission media may be involved in carrying one ormore sequences of one or more instructions to a CPU for execution. A buscarries the data to system RAM, from which a CPU retrieves and executesthe instructions. The instructions received by system RAM can optionallybe stored on a fixed disk either before or after execution by a CPU.Various forms of storage may likewise be implemented as well as thenecessary network interfaces and network topologies to implement thesame.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. The descriptions are not intended to limit the scope of theinvention to the particular forms set forth herein. Thus, the breadthand scope of a preferred embodiment should not be limited by any of theabove-described exemplary embodiments. It should be understood that theabove description is illustrative and not restrictive. To the contrary,the present descriptions are intended to cover such alternatives,modifications, and equivalents as may be included within the spirit andscope of the invention as defined by the appended claims and otherwiseappreciated by one of ordinary skill in the art. The scope of theinvention should, therefore, be determined not with reference to theabove description, but instead should be determined with reference tothe appended claims along with their full scope of equivalents.

TABLE A <!-- Copy and Paste this javascript in your page in the <head?section to display the ‘Get Podcast‘ button - <scripttype=“text/javascript” language=“javascript”src=“http://plugins.volomedia.com/new_agent/button_header.js”></script><!-- When a link to subscribe to a podcast is to be displayed somewhereon the page, the following HTML element <!-- that calls theVoloMediaSubscribe function in it's onClick handler should be coded asfollows: <a href=‘javascript:;‘onClick=“VoloMediaSubscribe(‘http://podcasts.nbc.com/nightly_news.xml‘,‘NBC Nightly News‘,‘http://podcasts.nbc.com/images/msnbc_logo.png‘,‘http://www.myanalytics.com/ma.js‘, ‘http://www.podcasts.nbc.com‘);return false;”>Get Podcast </a>// Create the VoloMedia Url Array var voloUrlArray = new Array( ); varvoloReportServer = “http://ticks.podbridge.com”; var voloImageServer =“http://plugins.volomedia.com/new_agent”; var voloScriptServer =“http://plugins.volomedia.com/new_agent”; var voloDefaultOfferUrl =“http://www.volomedia.com/rss/plugin-download- video.xml”; varvoloJSRelease = “new_agent”; var voloJSVersion = “1.2”; var voloClientID= VoloGenerateGUID( ); function VoloS4( ) {   return (((1+Math.random())*0x10000)|0).toString(16).substring(1); } // Function to help generatea pseudo unique client id function VoloGenerateGUID( ) {   return(VoloS4( )+VoloS4( )+“-”+VoloS4( )+“-”+VoloS4( )+“-”+VoloS4( )+“-”+VoloS4( )+VoloS4( )+VoloS4( )); } // Push a VoloMedia Url onto thearray stack. These urls will be called once the agent is accessiblefunction VoloPushUrl(url) {   // First check to see if this exact url isalready in the stack   var found = false;   for ( i = 0; i <voloUrlArray.length; i++ )   {     if ( voloUrlArray[i] == url )     {      found = true;       break;     }   }   if ( !found )    voloUrlArray.push(url); } function VoloReportEvent( ) {   // Thisfunction is going to accept a variable number of arguments in thefollowing order   // event -> the string representing the event type  // channel -> the url for the feed or channel that was requested   //client_id -> a unique id to represent this client   // referrer -> thereferring page for this code.   var voloEvent = null;   var voloChannel= null;   var voloClient_ID = null;   var voloReferrer = null;   // atthe very least we need an event argument   if ( arguments.length < 1 )    return;   voloEvent = arguments[0];   if ( arguments.length > 1 )    voloChannel = encodeURIComponent(arguments[1]);   if (arguments.length > 2 )     voloClient_ID = arguments[2];   else    voloClient_ID = voloClientID;   if ( arguments.length > 3 )    voloReferrer = encodeURIComponent(arguments[3]);   else    voloReferrer = encodeURIComponent(document.location);   var id =“voloImg”;   var voloBodyLoc =document.getElementsByTagName(“body”).item(0);   // Cleanup so we aren'tlittering the DOM with new elements   var imgObj =document.getElementById(id);   if ( null != imgObj )    voloBodyLoc.removeChild(imgObj);   var voloReportUrl =voloReportServer + “/vm.gif”;   var voloImgObj =document.createElement(“img”);   var voloRand = parseInt(Math.random()*99999999); // random number to get around caching issues  voloReportUrl += “?event=” + voloEvent;   if ( voloReferrer != null )  voloReportUrl += “&referrer=” + voloReferrer;   voloReportUrl +=“&rand=” + voloRand;   if ( voloChannel != null )     voloReportUrl +=“&channel_url=” + voloChannel;   if ( voloClient_ID != null )    voloReportUrl += “&client_id=” + voloClient_ID;   voloReportUrl +=“&PBver=” + voloJSRelease;     voloReportUrl += “&PV_jsVer=” +voloJSVersion;   voloImgObj.setAttribute(“src”, voloReportUrl);  voloImgObj.setAttribute(“id”, id);  voloBodyLoc.appendChild(voloImgObj);   //alert(“calling report url:” + voloReportUrl); } function VoloCallUrl(url) {   //alert(“callingurl: ” + url);   var id = “voloAgentScript”;   var voloHeadLoc =document.getElementsByTagName(“head”).item(0);   // Cleanup so we aren'tlittering the DOM with new elements   var scriptObj =document.getElementById(id);   if ( null != scriptObj )    voloHeadLoc.removeChild(scriptObj);     var voloScriptObj =document.createElement(“script”); // Add script object attributesvoloScriptObj.setAttribute(“type”, “text/javascript”);voloScriptObj.setAttribute(“src”, url);voloScriptObj.setAttribute(“language”, “javascript”);voloScriptObj.setAttribute(“id”, id);voloHeadLoc.appendChild(voloScriptObj); } function VoloPingAgent( ) {  var voloUrl = “http://127.0.0.1:10930/?cmd=Ping&ret=js”;  //alert(“Ping Agent: ” + voloUrl);   VoloCallUrl(voloUrl); } functionVoloIsAgentInstalled( ) {   return ( typeof(volomediaVersion) !=“undefined” ); } function VoloIsMac( ) {   returnnavigator.userAgent.toLowerCase( ).indexOf(“mac”) != −1; } functionVoloIsWindows( ) {   return navigator.userAgent.toLowerCase().indexOf(“windows”) != −1; } function VoloIsSupported( ) {   // OnlyMac and Windows are supported at this time   //return (VoloIsMac( ) | |VoloIsWindows( ));   return VoloIsWindows( ); } functionVoloMediaSubscribe(url, title, logo) {   if ( typeof(url) == “undefined”) return false;     VoloReportEvent(“GPC”, url); if ( !VoloIsSupported() ) {     // navigate to itpc://   if (url.indexOf(“http://”) == 0)//replace with itpc     url = url.replace(“http://”, “itpc://”);      else if (url.indexOf(“HTTP://”) == 0) //replace with itpc     url= url.replace(“HTTP://”, “itpc://”);   else     url = “itpc://” + url;  window.location = url;   return false; } var request = “”; if (VoloIsAgentInstalled( ) ) // Subscribe for an RSS feed   {     request =“http://127.0.0.1:10930/?cmd=Subscribe&ret=js”;   }   else // Installand subscribe for an RSS feed   {     request = voloScriptServer +“/install_popup.php?cmd=Install”;     VoloReportEvent(“DPV”, url);   }  if ( logo != undefined )     request += “&logo=” +encodeURIComponent(logo);   if ( title != undefined )     request +=“&title=” + encodeURIComponent(title);   if ( url != undefined )    request += “&url=” + encodeURIComponent(url);   // add the client idand referrer to the url   request += “&client_id=” + voloClientID;  request += “&referrer=” + encodeURIComponent(document.location);  VoloCallUrl(request);   return false; } functionVoloMediaSubscribeOffer(url, title, logo, offer_url) {   if (!VoloIsAgentInstalled( ) )   {     if ( typeof(offer_url) == “undefined”)       offer_url = voloDefaultOfferUrl;     encoded_offer_url =encodeURIComponent(offer_url);     push_url =‘http://127.0.0.1:10930/?cmd=Subscribe&url=’ + encoded_offer_url;    VoloPushUrl(push_url);     VoloMediaSubscribe(url, title, logo);   }  else   {     VoloMediaSubscribe(url, title, logo);   }   return false;} function VoloLaunchUrls( ) {   if ( VoloIsAgentInstalled( ) )   {    //alert(“Check Agent is launch urls: ” + voloUrlArray);     // Checkif there are any subscriptions that need to go out while (  voloUrlArray.length > 0 )     {       var url = voloUrlArray.shift( );      //alert(“Add Url: ” + url);       VoloCallUrl(url);     }   }  else   {     //alert(“Agent isn't running”);    setTimeout(“VoloCheckAgent( )”, 2000);   } } functionVoloCheckAgent( ) {     //alert(“VoloCheckAgent”);     volomediaVersion= undefined;     VoloPingAgent( );     if ( voloUrlArray.length > 0 )    {       // set a timeout to check the agent      setTimeout(“VoloLaunchUrls( )”, 500);     } } // Ping the agent tosee if it's running VoloPingAgent( );

1. (canceled)
 2. A computer-implemented method for analyzing episodicmedia consumption, the method comprising: receiving information over acommunication network regarding an association between at least onesubscribing user and an insertable content file; automatically sendingan episodic media file over the communication network to a client deviceassociated with the at least one subscribing user, wherein the episodicmedia file is split into two parts at an insertion point, and at least aportion of the insertable content file is stitched between the two partsto create a single new media file comprising both the episodic mediafile and the insertable content file; and receiving usage informationover the communication network regarding the subscribing user, whereinthe usage information indicates whether at least a portion of theinsertable content file was consumed by the at least one subscribinguser during a time period in which the client device was off-line. 3.The computer-implemented method of claim 2, further comprising encodingthe new media file for compatibility with the client device.
 4. Thecomputer-implemented method of claim 2, further comprising encoding thenew media file for compatibility with two or more client device types.5. The computer-implemented method of claim 2, further comprisinganalyzing the received usage information to identify at least onerecommended media content file, wherein identifying the at least onerecommended media content file is based on metadata of the episodicmedia file.
 6. The computer-implemented method of claim 5, furthercomprising transmitting a recommendation to the client device regardingthe recommended media content file, the recommendation includingmetadata to cause the recommended media content file to be downloaded tothe client device.
 7. The computer-implemented method of claim 2,wherein the received usage information comprises a plurality of eventindicators regarding the new media file, the plurality of eventindicators comprising an indication of one or more of: success indownloading the new media file, failure in downloading the new mediafile, playback completion of the insertable content file, and a playcount of the episodic media file.
 8. The computer-implemented method ofclaim 2, wherein automatically sending the episodic media file over thecommunication network to the client device comprises matching theinsertable content file with the at least one subscribing userassociated with the client device, and further comprising re-encodingthe single new media file to have a uniform matching profile and to becompatible with the client device of the at least one subscribing user.9. A system for analyzing episodic media consumption, the systemcomprising: a match server configured for receiving information over acommunication network regarding an association between at least onesubscribing user and an insertable content file; a hosting servercommunicatively coupled with the match server, the hosting serverconfigured for automatically sending an episodic media file over thecommunication network to a client device associated with the at leastone subscribing user, wherein the episodic media file is split into twoparts at an insertion point, and at least a portion of the insertablecontent file is stitched between the two parts to create a single newmedia file comprising both the episodic media file and the insertablecontent file; and a database communicatively coupled with the hostingserver, the database configured for receiving usage information over thecommunication network regarding the subscribing user, wherein the usageinformation indicates whether at least a portion of the insertablecontent file was consumed by the at least one subscribing user during atime period in which the client device was off-line.
 10. The system ofclaim 9, wherein the hosting server further encodes the new media filefor compatibility with the client device.
 11. The system claim 9,wherein the hosting server further encodes the new media file forcompatibility with two or more client device types.
 12. The system ofclaim 9, wherein the hosting server further analyzes received usageinformation to identify at least one recommended media content file,wherein identifying the at least one recommended media content file isbased on metadata of the episodic media file.
 13. The system of claim12, wherein the hosting server further transmits a recommendation to theclient device regarding the at least one recommended media content file,the recommendation including metadata to cause the recommended mediacontent file to be downloaded to the client device.
 14. The system ofclaim 9, wherein the received usage information comprises a plurality ofevent indicators regarding the new media file, the plurality of eventindicators comprising an indication of one or more of: success indownloading the new media file, failure in downloading the new mediafile, playback completion of the insertable content file, and a playcount of the episodic media file.
 15. The system of claim 9, wherein thehosting server further automatically sends the media file over thecommunication network to the client device by matching the insertablecontent file with the at least one subscribing user associated with theclient device, and re-encodes the new media file to have a uniformmatching profile and to be compatible with the client device of the atleast one subscribing user.
 16. A non-transitory computer-readablestorage medium, having embodied thereon a program executable by aprocessor to perform a method for analyzing episodic media consumption,the method comprising: receiving information over a communicationnetwork regarding an association between at least one subscribing userand an insertable content file; automatically sending an episodic mediafile over the communication network to a client device associated withthe at least one subscribing user, wherein the episodic media file issplit into two parts at an insertion point, and at least a portion ofthe insertable content file is stitched between the two parts to createa single new media file comprising both the episodic media file and theinsertable content file; and receiving usage information over thecommunication network regarding the subscribing user, wherein the usageinformation indicates whether at least a portion of the insertablecontent file was consumed by the at least one subscribing user during atime period in which the client device was off-line.
 17. Thenon-transitory computer-readable storage medium of claim 16, furthercomprising instructions executable to encode the new media file forcompatibility with the client device.
 18. The non-transitorycomputer-readable storage medium of claim 16, further comprisinginstructions executable to encode the new media file for compatibilitywith two or more client device types.
 19. The non-transitorycomputer-readable storage medium of claim 16, further comprisinginstructions executable to analyze the received usage information toidentify at least one recommended media content file, whereinidentifying the at least one recommended media content file is based onmetadata of the episodic media file.
 20. The non-transitorycomputer-readable storage medium of claim 16, further comprisinginstructions executable to transmit a recommendation to the clientdevice regarding the at least one recommended media content file, therecommendation including metadata to cause the recommended media contentfile to be downloaded to the client device.
 21. The non-transitorycomputer-readable storage medium of claim 16, wherein the received usageinformation comprises a plurality of event indicators regarding the newmedia file, the plurality of event indicators comprising an indicationof one or more of: an episode download success, an episode downloadfailure, playback completion of the insertable content file, and a playcount of the episodic media file.